- This video doorbell camera has just as many features are my Ring - and no subscription required
- LG is giving away free 27-inch gaming monitors, but this is the last day to grab one
- I tested this Eufy security camera and can't go back to grainy night vision
- I replaced my iPhone with a premium dumbphone - here's my verdict after a month
- Build your toolkit with the 10 DIY gadgets every dad should have
General Boot from iSCSI SAN Recommendations
General Boot from iSCSI SAN Recommendations
If you plan to set up and use an iSCSI LUN as the boot device for your host, you need to follow certain general guidelines.
The following guidelines apply to booting from independent hardware iSCSI and iBFT.
■
Review any vendor recommendations for the hardware you use in your boot configuration.
■
For installation prerequisites and requirements, review vSphere Installation and Setup.
■
Use static IP addresses to reduce the chances of DHCP conflicts.
■
Use different LUNs for VMFS datastores and boot partitions.
■
Configure proper ACLs on your storage system.
■
The boot LUN should be visible only to the host that uses the LUN. No other host on the SAN should be permitted to see that boot LUN.
■
If a LUN is used for a VMFS datastore, it can be shared by multiple hosts. ACLs on the storage systems can allow you to do this.
■
Configure a diagnostic partition.
■
With independent hardware iSCSI only, you can place the diagnostic partition on the boot LUN. If you configure the diagnostic partition in the boot LUN, this LUN cannot be shared across multiple hosts. If a separate LUN is used for the diagnostic partition, it can be shared by multiple hosts.
■
If you boot from SAN using iBFT, you cannot set up a diagnostic partition on a SAN LUN. To collect your host’s diagnostic information, use the vSphere ESXi Dump Collector on a remote server. For information about the ESXi Dump Collector, see vSphere Installation and Setup and vSphere Networking.